@vishnu-khanth Could we add tests here to validate this issue does not exist and works OK ?

Tests are existing for covering this scenario and passing but invalid memory reference is done which is caught by valgrind.

May be new test can be added separately where loader supports DDI Ext.
One null driver supports DDI Ext and handle translation doesn't happen for handles given by this driver.
And another null driver doesn't support DDI Ext and handles translation happens for the handles given by this driver.

Looks like it got added as multi commits in oneapi-src:master

Tests are existing for covering this scenario and passing but invalid memory reference is done which is caught by valgrind.

If tests are existing, but invalid memory reference should be caught right ?
Can we add more validations to existing tests to consider this condition as well

May be new test can be added separately where loader supports DDI Ext.
One null driver supports DDI Ext and handle translation doesn't happen for handles given by this driver.
And another null driver doesn't support DDI Ext and handles translation happens for the handles given by this driver.

Sure.. Please create a JIRA to add this.